Install PAM modules and systemd units into /usr
Since Debian trixie all files need to be installed into their canonical
location under /usr.
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
1061348
Forwarded: https://github.com/MariaDB/server/pull/4065
Gbp-Pq: Name install-files-into-usr.patch
cmake: add support for reproducible buildS
We should use relative path not absolute path. We can use target without
breaking reproducibility.
This patch can be removed once MariaDB ships with Mroonga v12.00+ that has
https://github.com/mroonga/mroonga/commit/
27caeb9b8ce7fa432b1251eca475b517c6902a6c
Origin: https://github.com/mroonga/mroonga/issues/298#issuecomment-
1030815927
Bug: https://github.com/mroonga/mroonga/issues/298
Forwarded: not-needed
Gbp-Pq: Name mroonga-mrn-lib-dirs-path-reproducible-build.patch
mariadb (1:11.8.6-2) unstable; urgency=medium
[ Aquila Macedo ]
* Add systemd hardening patch for MariaDB units (Closes: #
1123021)
[ Otto Kekäläinen ]
* Add Lintian override for potentially false new error about embedded
libminizip
* Remove patch for x32 compilation now supposedly fixed upstream in
ff4209f
* Update patch statuses and Forwarded fields to match latest
* Fix path to mariadb-server.README in mariadb-secure-install
(Closes: #
1127863)
* Add preliminary upstream patch to fix MDEV-38811 that affected Akonadi and
any other use case that relies on 'skip-grant-tables' (Closes: #
1127431)
* Add functional AppArmor profile for MariaDB 11.8 but keep it in 'complain'
mode for now to collect real usage experience, and enabling 'enforce' mode
some day in the future when likelihood of unanticipated AppArmor denials
is close to zero (Closes: #875890)
[dgit import unpatched mariadb 1:11.8.6-2]